Overlay network identity-based relay

ABSTRACT

Embodiments are directed to a relay that receives packets from a source gateway associated with a source gateway identifier (GID) and a target GID associated with a target gateway where each GID is separate from a network address or a hostname of the source gateway or the target gateway. The relay determines a connection route based on an association between the connection route and an ingress identifier obtained from the packets. The relay provides the connection route based on the source GID and the target GID. The relay determines network address information associated with the target gateway based on the connection route. And, the relay forwards the packets provided by the source gateway to the target gateway based on the network address information.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This Utility Patent Application is a Continuation of U.S. patentapplication Ser. No. 16/120,043 filed on Aug. 31, 2018, now U.S. Pat.No. 10,200,281 issued on Feb. 5, 2019, which is a Continuation of U.S.patent application Ser. No. 15/924,148 filed on Mar. 16, 2018, now U.S.Pat. No. 10,069,726 issued on Sep. 4, 2018, the benefit of which isclaimed under 35 U.S.C. § 120, and the contents of which are eachfurther incorporated in entirety by reference.

TECHNICAL FIELD

The present invention relates generally to network management, and moreparticularly, but not exclusively, to managing communication over anetwork in which host identity is distinct from its topological locationon a network.

BACKGROUND

Typical network communication protocols, such as, Internet Protocol (IP)deliver network packets from a source host to a destination host basedon an IP address. Traditionally, IP addresses have served a dual purposeas a host's identity and location. This has led to challenges securingthe various hosts and networks in modern distributed networkingenvironments.

For instance, network packets often include a source network addressthat may be used by the target host to address and route return packets.However, in some cases target hosts may use the source network addressto determine the identity of the source host. In some cases, this dualuse may cause networks or services to be vulnerable to man-in-the-middleattacks based on network packets that include false or spoofed networkaddresses. Other security challenges enabled in part by this dual roleof network addresses may include denial of service attacks, replayattacks, or the like. Also, since modern computing environments oftenemploy ephemeral and/or non-unique network addresses, using networkaddress to provide host identity poses challenges, as modern hosts, e.g.cell phones, frequently change location on the network. Thus, it is withrespect to these and other considerations that these innovations aremade.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the present innovationsare described with reference to the following drawings. In the drawings,like reference numerals refer to like parts throughout the variousfigures unless otherwise specified. For a better understanding of thedescribed innovations, reference will be made to the followingDescription of Various Embodiments, which is to be read in associationwith the accompanying drawings, wherein:

FIG. 1 shows components of one embodiment of an environment in whichembodiments of the invention may be practiced;

FIG. 2 shows one embodiment of a client computer that may be included ina system in accordance with at least one of the various embodiments;

FIG. 3 shows one embodiment of a network computer, in accordance with atleast one of the various embodiments;

FIG. 4 illustrates a logical schematic of a network that includesoverlay networks, node computers, gateway computers, relay computer inaccordance with at least one of the various embodiments;

FIG. 5 illustrates a logical representation of a system forcommunicating in a network in accordance with one or more of the variousembodiments;

FIG. 6 illustrates a portion of a policy for defining connection routesallowed between pairs of gateway computers in accordance with one ormore of the various embodiments;

FIG. 7 illustrates connection information for accumulating at least someof the information that enables overlay network identity-based relaybetween gateway computers in accordance with one or more of the variousembodiments;

FIG. 8 illustrates a logical representation of a standards compatiblenetwork packets that may be used to communicate between gatewaycomputers in accordance with one or more of the various embodiments;

FIG. 9 illustrates an overview flowchart of a process for overlaynetwork identity-based relay in accordance with one or more of thevarious embodiments; and

FIG. 10 illustrates a sequence diagram for overlay networkidentity-based relay in accordance with one or more of the variousembodiments.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Various embodiments now will be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of illustration, specific exemplary embodiments bywhich the invention may be practiced. The embodiments may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of the embodiments to those skilled in the art.Among other things, the various embodiments may be methods, systems,media or devices.

Accordingly, the various embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment or an embodimentcombining software and hardware aspects. The following detaileddescription is, therefore, not to be taken in a limiting sense.

Throughout the specification and claims, the following terms take themeanings explicitly associated herein, unless the context clearlydictates otherwise. Phrases, such as, “in one embodiment,” “in one ormore embodiments, “some embodiments,” “in one or more of the variousembodiments,” or the like, as used herein do not necessarily refer tothe same embodiment, though it may. Furthermore, phrases, such as, “inone embodiment,” “in one or more embodiments, “some embodiments,” “inone or more of the various embodiments,” or the like, as used herein donot necessarily refer to a different embodiment, although it may. Thus,as described below, various embodiments may be readily combined, withoutdeparting from the scope or spirit of the invention. Similarly, phrases,such as, “in one or more embodiments, “some embodiments,” “in one ormore of the various embodiments”, or the like.

In addition, as used herein, the term “or” is an inclusive “or”operator, and is equivalent to the term “and/or,” unless the contextclearly dictates otherwise. The term “based on” is not exclusive andallows for being based on additional factors not described, unless thecontext clearly dictates otherwise. In addition, throughout thespecification, the meaning of “a,” “an,” and “the” include pluralreferences. The meaning of “in” includes “in” and “on.”

For example embodiments, the following terms are also used hereinaccording to the corresponding meaning, unless the context clearlydictates otherwise.

As used herein the terms “mesh network,” “industrial network” refer to anetwork of industrial computer/machines, workstations, client computers,gateway computers, or the like. The term mesh network used hereindescribes both the typical network topology of a network in anindustrial operation environment as well as more generally, a networkedsystem used to perform operations in an industrial environment, such as,as factory floor, manufacturing complex, oil refinery, or the like. Inthe interest of clarity such networks (including machines and computerson the network) are referred to as mesh networks even when theirtopology and/or configuration is not strictly a “mesh” network and/orpartial “mesh” network.

As used herein the term “physical network” refers to the actualcommunication network that interconnects one or more computers ornetworks. The physical network may be a physical or native networkdevice/components used to connect one or more computers or industrialdevices (machines) in a network. Physical networks include networkinterfaces, wire, wireless hotspots, switches, routers, repeaters, orthe like, that comprise the physical network Also, physical networks maybe considered to include the native communication protocols, networktopology, and so on, that may be used to setup a mesh network in variousenvironments. In some cases, physical networks may be arranged to enableopen communication between node computers, (e.g., machines,workstations, client computers, and so on), gateway computers,management platform computers, relay computers, or the like, that are onthe physical network.

As used herein the terms “node,” and “node computer” refer to computersthat are endpoint computers interconnected over a physical network. Nodecomputers may include client computers, smart phones, video cameras,sensors, network computers, industrial workstations, press machines,robots, packaging machines, automated milling machines, automatedprinting presses, pumps, valves, boilers, or the like. Node computersare considered to be computers or devices connected to the physicalnetwork exclusive of gateway computers, relay computers, managementplatform server computers, or the like. Nodes gain access to thenetworks managed management platform via gateway computers

As used herein the terms “source node,” and “source node computer” referto a node computer that is the originating endpoint of a networkcommunication.

As used herein the terms “target node,” and “target node computer” referto a node computer that is the ultimate intended destination of acommunication. In some embodiments, a source node computer may becommunicating to one or more other node computers over anindustrial/mesh network. These intended recipients of thesecommunication may be considered target node computers. Accordingly, anode computer may be a target node computer if it receivescommunications and it may be a source node computer if it sendscommunications.

As used herein the terms “gateway,” or “gateway computer” refer tocomputers connected to a network that are disposed between the nodecomputers and the physical network. Gateway computers may be networkcomputers that may be arranged to provide security, access control,communication routing, or the like, for mesh networks or overlaynetworks. In some embodiments, gateway computers may be configured byanother network computer, such as, a management platform computer.

As used herein the term “relay computer”, or “relay” refer to one ormore computers that serve as intermediaries for establishing connectionsbetween gateway computers that may be on different networks. In somecases, relay computers may be associated with network addresses that maybe reached from more than one network. In some embodiments, relaycomputers may be configured by another network computer, such as, amanagement platform computer.

As used herein the term “ingress identifier” refers to a value includedin outbound network packet provided by gateway computers. Ingressidentifiers may be included in each packet sent from a gateway computer.Ingress identifiers may be visible to relay computers. For example, insome embodiments, ingress identifiers may be security parameter index(SPI) values included in network packets comprising a network connectionthat is secured using Internet Protocol security (IPSEC) protocol.Accordingly, in this example, the value of the SPI may be available torelay computers even though most of the packet is encrypted.

As used herein the term “network address” refers to a value or valuesused for locating an endpoint in a network. In some embodiments,endpoints may include services, networks, network computers, clientcomputers, applications, firewall, router, load balancers, nodecomputers, gateway computers, relay computers, management platformcomputers, or the like. A network address may be assumed to comprise oneor more components, such as, Internet Protocol (IP) address, othernetwork address, a port number, VLAN identifier, tunnel identifier,routing interface identifier, physical interface identifier, a protocolidentifier, or the like, or combination thereof. In some embodiments,port numbers may be TCP or UDP port numbers. For example, in someembodiments, a network address in a network may be assumed to include anIP address and a port. The particular constituent components or formatsof network addresses may vary to meet one or more characteristics orrequirements of the networks or communication protocols being used.

As used herein the term “public key” refers to the public key of anasymmetric cryptographic key pair. A public key may be used as apublicly known identifier for cryptographic identity authentication.

As used herein the term “private key” refers to the private or secretkey of an asymmetric cryptographic key pair. A private key is assumed tobe known only to the party identified by the corresponding public key. Aprivate key is used by the identified party to authenticate its identityto other parties.

As used herein the term “public key pair” refers to an asymmetriccryptographic key pair consisting of public and private keys. Forexample, Rivest-Shamir-Adelman (RSA) key pairs, Diffie-Hellman keypairs, or Digital Signature Algorithm (DSA) key pairs are such publickey pairs.

The following briefly describes embodiments of the invention in order toprovide a basic understanding of some aspects of the invention. Thisbrief description is not intended as an extensive overview. It is notintended to identify key or critical elements, or to delineate orotherwise narrow the scope. Its purpose is merely to present someconcepts in a simplified form as a prelude to the more detaileddescription that is presented later.

Briefly stated, various embodiments are directed to managingcommunication over a network for overlay network identity based relays.

In one or more of the various embodiments, a relay engine may beinstantiated to perform one or more actions for overlay network identitybased relays.

In one or more of the various embodiments, the relay engine may bearranged to receive one or more packets from a source gateway. The oneor more packets may be associated with a source gateway identifier (GID)that may correspond to the source gateway and a target GID that may beassociated with a target gateway such that each GID is separate from anetwork address or a hostname of the source gateway or the targetgateway.

In one or more of the various embodiments, the relay engine may bearranged to determine a connection route based on an association betweenthe connection route and an ingress identifier such that the ingressidentifier may be obtained from the one or more packets from the sourcecomputer that may be separate from the source GID.

In one or more of the various embodiments, the relay engine may bearranged to provide the connection route based on the source GID and thetarget GID such that the connection route may be associated with boththe source GID and the target GID.

In one or more of the various embodiments, the relay engine may bearranged to determine network address information associated with thetarget gateway based on the connection route. And, in one or more of thevarious embodiments, the relay engine may be arranged to forward the oneor more packets provided by the source gateway to the target gatewaybased on the network address information.

In one or more of the various embodiments, the relay engine may bearranged to receive an initial handshake message from another gateway.In one or more of the various embodiments, the relay engine may bearranged to determine a delay period based on one or more of, the GIDassociated with other gateway, the GID associated with another targetgateway, policy associated with the relay, one or more performancemetrics, or the like. In one or more of the various embodiments, upon anexpiration of the delay period, a response message may be provided tothe other gateway such that a first relay that provides the responsemessage to the other gateway is used to establish the connection route.

In one or more of the various embodiments, the relay engine may bearranged to receive an initial handshake message from another gateway.In one or more of the various embodiments, another ingress identifierand another GID associated with the other gateway may be obtained. And,in one or more of the various embodiments, the other ingress identifiermay be employed to index the other GID data store.

In one or more of the various embodiments, the relay engine may bearranged to translate the one or more packets from the source gatewayfrom a first network protocol to a second network protocol that iscompatible with the target gateway.

In one or more of the various embodiments, the relay engine may bearranged to monitor the one or more packets to identify keep-alivepackets. And, in one or more of the various embodiments, the relayengine may be arranged to drop one or more connections between one ormore gateways associated with keep-alive packets based on one or moreperformance metrics.

In one or more of the various embodiments, the relay engine may bearranged to drop one or more connections between one or more gatewaysbased on one or more performance metrics exceeding one or more definedthresholds.

In one or more of the various embodiments, a gateway engine may beinstantiated to broadcast an initial handshake message to one or morerelays. And, in one or more of the various embodiments, the gatewayengine may establish a connection with a relay that is first to respondto the initial handshake message.

In one or more of the various embodiments, a platform engine may beinstantiated to provide policy information that may define one or moreconnection routes in an overlay network to one or more relay engines andto one or more gateways such that each connection route may beassociated with two or more GIDs.

Illustrated Operating Environment

FIG. 1 shows components of one embodiment of an environment in whichembodiments of the invention may be practiced. Not all of the componentsmay be required to practice the invention, and variations in thearrangement and type of the components may be made without departingfrom the spirit or scope of the invention. As shown, system 100 of FIG.1 includes local area networks (LANs)/wide area networks(WANs)-(network) 110, wireless network 108, client computers 102-105,management platform server computer 116, gateway computers 118, relaycomputers 120, node computers 122, or the like.

At least one embodiment of client computers 102-105 is described in moredetail below in conjunction with FIG. 2. In one embodiment, at leastsome of client computers 102-105 may operate over one or more wiredand/or wireless networks, such as networks 108, and/or 110. Generally,client computers 102-105 may include virtually any computer capable ofcommunicating over a network to send and receive information, performvarious online activities, offline actions, or the like.

For example, client computers 102-105 may be configured to operate as aweb server, client application, media player, mobile telephone, gameconsole, desktop computer, or the like. It should be recognized thatmore or less client computers (as shown in FIG. 1) may be includedwithin a system such as described herein, and embodiments are thereforenot constrained by the number or type of client computers employed.

Computers that may operate as client computer 102 may include computersthat typically connect using a wired or wireless communications mediumsuch as personal computers, multiprocessor systems, microprocessor-basedor programmable electronic devices, network PCs, or the like. In someembodiments, client computers 102-105 may include virtually any portablecomputer capable of connecting to another computer and receivinginformation such as, laptop computer 103, mobile computer 104, tabletcomputers 105, or the like. However, portable computers are not solimited and may also include other portable computers such as cellulartelephones, display pagers, radio frequency (RF) devices, infrared (IR)devices, Personal Digital Assistants (PDAs), handheld computers,wearable computers, integrated devices combining one or more of thepreceding computers, or the like. As such, client computers 102-105typically range widely in terms of capabilities and features. Moreover,client computers 102-105 may access various computing applications,including a browser, or other web-based application.

A web-enabled client computer may include a browser application that isconfigured to receive and to send web pages, web-based messages, and thelike. The browser application may be configured to receive and displaygraphics, text, multimedia, and the like, employing virtually anyweb-based language, including a wireless application protocol messages(WAP), and the like. In one embodiment, the browser application isenabled to employ Handheld Device Markup Language (HDML), WirelessMarkup Language (WML), WMLScript, JavaScript, Standard GeneralizedMarkup Language (SGML), HyperText Markup Language (HTML), eXtensibleMarkup Language (XML), JavaScript Object Notation (JSON), or the like,to display and send a message. In one embodiment, a user of the clientcomputer may employ the browser application to perform variousactivities over a network (online). However, another application mayalso be used to perform various online activities.

Node computers 122 represent one or more client computer, networkcomputer, or network devices, or the like, that may be arranged toaccess networks via a gateway computer. Each node computer may beassociated with a gateway computer that enable network access to othernode computers, gateway computers, or the like. Node computers 122 maybe arranged to communicate with their associate gateway computer.Accordingly, in some embodiments, their gateway computer may route thenode computer communication according to policy provided by a managementplatform server, such as, management platform server computer 116.

Wireless network 108 is configured to couple client computers 103-105and its components with network 110. Wireless network 108 may includeany of a variety of wireless sub-networks that may further overlaystand-alone ad-hoc networks, and the like, to provide aninfrastructure-oriented connection for client computers 103-105. Suchsub-networks may include mesh networks, Wireless LAN (WLAN) networks,cellular networks, and the like. In one embodiment, the system mayinclude more than one wireless network.

Wireless network 108 may further include an autonomous system ofterminals, gateways, routers, and the like connected by wireless radiolinks, and the like. These connectors may be configured to move freelyand randomly and organize themselves arbitrarily, such that the topologyof wireless network 108 may change rapidly.

Wireless network 108 may further employ a plurality of accesstechnologies including 2nd (2G), 3rd (3G), 4th (4G) 5th (5G) generationradio access for cellular systems, WLAN, Wireless Router (WR) mesh, andthe like. Access technologies such as 2G, 3G, 4G, 5G, and future accessnetworks may enable wide area coverage for mobile computers, such asclient computers 103-105 with various degrees of mobility. In onenon-limiting example, wireless network 108 may enable a radio connectionthrough a radio network access such as Global System for Mobilcommunication (GSM), General Packet Radio Services (GPRS), Enhanced DataGSM Environment (EDGE), code division multiple access (CDMA), timedivision multiple access (TDMA), Wideband Code Division Multiple Access(WCDMA), High Speed Downlink Packet Access (HSDPA), Long Term Evolution(LTE), and the like. In essence, wireless network 108 may includevirtually any wireless communication mechanism by which information maytravel between client computers 103-105 and another computer, network, acloud-based network, a cloud instance, or the like.

Network 110 is configured to couple network computers with othercomputers, including, management platform server computer 116, gatewaycomputers 118, relay computers 120, node computers 122, client computers102-105 through wireless network 108, or the like. Network 110 isenabled to employ any form of computer readable media for communicatinginformation from one electronic device to another. Also, network 110 caninclude the Internet in addition to local area networks (LANs), widearea networks (WANs), direct connections, such as through a universalserial bus (USB) port, other forms of computer-readable media, or anycombination thereof. On an interconnected set of LANs, including thosebased on differing architectures and protocols, a router acts as a linkbetween LANs, enabling messages to be sent from one to another. Inaddition, communication links within LANs typically include twisted wirepair or coaxial cable, while communication links between networks mayutilize analog telephone lines, full or fractional dedicated digitallines including T1, T2, T3, and T4, and/or other carrier mechanismsincluding, for example, E-carriers, Integrated Services Digital Networks(ISDNs), Digital Subscriber Lines (DSLs), wireless links includingsatellite links, or other communications links known to those skilled inthe art. Moreover, communication links may further employ any of avariety of digital signaling technologies, including without limit, forexample, DS-0, DS-1, DS-2, DS-3, DS-4, OC-3, OC-12, OC-48, or the like.Furthermore, remote computers and other related electronic devices couldbe remotely connected to either LANs or WANs via a modem and temporarytelephone link. In one embodiment, network 110 may be configured totransport information of an Internet Protocol (IP).

Additionally, communication media typically embodies computer readableinstructions, data structures, program modules, or other transportmechanism and includes any information delivery media. By way ofexample, communication media includes wired media such as twisted pair,coaxial cable, fiber optics, wave guides, and other wired media andwireless media such as acoustic, RF, infrared, and other wireless media.

Although FIG. 1 illustrates management platform server computer 116,gateway computers 118, relay computers 120, node computers 122 each as asingle computer, the innovations or embodiments are not so limited. Forexample, one or more functions of management platform server computer116, gateway computers 118, relay computers 120, node computers 122 orthe like, may be distributed across one or more distinct networkcomputers. Moreover, management platform server computer 116, gatewaycomputers 118, relay computers 120, node computers 122 are not limitedto a particular configuration such as the one shown in FIG. 1. Thus, inone or more embodiments, management platform server computer 116,gateway computers 118, relay computers 120, node computers 122may beimplemented using a plurality of network computers. In otherembodiments, management platform server computer 116, gateway computers118, relay computers 120, node computers 122 may operate as a pluralityof network computers within a cluster architecture, a peer-to-peerarchitecture, or the like. Also, in some embodiments, one or moreprocessors on one or more network computers may be arranged to performone or more actions of management platform server computer 116, gatewaycomputers 118, relay computers 120, node computers 122, or the like.Further, in at least one of the various embodiments, management platformserver computer 116, gateway computers 118, relay computers 120, nodecomputers 122 may be implemented using one or more cloud instances inone or more cloud computing environments. Likewise, in at least one ofthe various embodiments, management platform server computer 116,gateway computers 118, relay computers 120, node computers 122 may beimplemented using one or more container instances in one or morecontainer computers environments.

Illustrative Client computer

FIG. 2 shows one embodiment of client computer 200 that may include manymore or less components than those shown. Client computer 200 mayrepresent, for example, at least one embodiment of mobile computers orclient computers 102-105 shown in FIG. 1.

Client computer 200 may include processor 202 in communication withmemory 204 via bus 228. Client computer 200 may also include powersupply 230, network interface 232, audio interface 256, display 250,keypad 252, illuminator 254, video interface 242, input/output interface238, haptic interface 264, global positioning systems (GPS) receiver258, open air gesture interface 260, temperature interface 262,camera(s) 240, projector 246, pointing device interface 266,processor-readable stationary storage device 234, and processor-readableremovable storage device 236. Client computer 200 may optionallycommunicate with a base station (not shown), or directly with anothercomputer. And in one embodiment, although not shown, a gyroscope may beemployed within client computer 200 to measuring and/or maintaining anorientation of client computer 200.

Power supply 230 may provide power to client computer 200. Arechargeable or non-rechargeable battery may be used to provide power.The power may also be provided by an external power source, such as anAC adapter or a powered docking cradle that supplements and/or rechargesthe battery.

Network interface 232 includes circuitry for coupling client computer200 to one or more networks, and is constructed for use with one or morecommunication protocols and technologies including, but not limited to,protocols and technologies that implement any portion of the OSI modelfor mobile communication (GSM), CDMA, time division multiple access(TDMA), UDP, TCP/IP, SMS, MMS, GPRS, WAP, UWB, WiMax, SIP/RTP, GPRS,EDGE, WCDMA, LTE, UMTS, OFDM, CDMA2000, EV-DO, HSDPA, or any of avariety of other wireless communication protocols. Network interface 232is sometimes known as a transceiver, transceiving device, or networkinterface card (MC).

Audio interface 256 may be arranged to produce and receive audio signalssuch as the sound of a human voice. For example, audio interface 256 maybe coupled to a speaker and microphone (not shown) to enabletelecommunication with others and/or generate an audio acknowledgementfor some action. A microphone in audio interface 256 can also be usedfor input to or control of client computer 200, e.g., using voicerecognition, detecting touch based on sound, and the like.

Display 250 may be a liquid crystal display (LCD), gas plasma,electronic ink, light emitting diode (LED), Organic LED (OLED) or anyother type of light reflective or light transmissive display that can beused with a computer. Display 250 may also include a touch interface 244arranged to receive input from an object such as a stylus or a digitfrom a human hand, and may use resistive, capacitive, surface acousticwave (SAW), infrared, radar, or other technologies to sense touch and/orgestures.

Projector 246 may be a remote handheld projector or an integratedprojector that is capable of projecting an image on a remote wall or anyother reflective object such as a remote screen.

Video interface 242 may be arranged to capture video images, such as astill photo, a video segment, an infrared video, or the like. Forexample, video interface 242 may be coupled to a digital video camera, aweb-camera, or the like. Video interface 242 may comprise a lens, animage sensor, and other electronics. Image sensors may include acomplementary metal-oxide-semiconductor (CMOS) integrated circuit,charge-coupled device (CCD), or any other integrated circuit for sensinglight.

Keypad 252 may comprise any input device arranged to receive input froma user. For example, keypad 252 may include a push button numeric dial,or a keyboard. Keypad 252 may also include command buttons that areassociated with selecting and sending images.

Illuminator 254 may provide a status indication and/or provide light.Illuminator 254 may remain active for specific periods of time or inresponse to events. For example, when illuminator 254 is active, it maybacklight the buttons on keypad 252 and stay on while the clientcomputer is powered. Also, illuminator 254 may backlight these buttonsin various patterns when particular actions are performed, such asdialing another client computer. Illuminator 254 may also cause lightsources positioned within a transparent or translucent case of theclient computer to illuminate in response to actions.

Further, client computer 200 may also comprise hardware security module(HSM) 268 for providing additional tamper resistant safeguards forgenerating, storing and/or using security/cryptographic information suchas, keys, digital certificates, passwords, passphrases, two-factorauthentication information, or the like. In some embodiments, hardwaresecurity module may be employed to support one or more standard publickey infrastructures (PKI), and may be employed to generate, manage,and/or store keys pairs, or the like. In some embodiments, HSM 268 maybe a stand-alone computer, in other cases, HSM 268 may be arranged as ahardware card that may be added to a client computer.

Client computer 200 may also comprise input/output interface 238 forcommunicating with external peripheral devices or other computers suchas other client computers and network computers. The peripheral devicesmay include an audio headset, display screen glasses, remote speakersystem, remote speaker and microphone system, and the like. Input/outputinterface 238 can utilize one or more technologies, such as UniversalSerial Bus (USB), Infrared, WiFi, WiMax, Bluetooth™, and the like.

Haptic interface 264 may be arranged to provide tactile feedback to auser of the client computer. For example, the haptic interface 264 maybe employed to vibrate client computer 200 in a particular way whenanother user of a computer is calling. Temperature interface 262 may beused to provide a temperature measurement input and/or a temperaturechanging output to a user of client computer 200. Open air gestureinterface 260 may sense physical gestures of a user of client computer200, for example, by using single or stereo video cameras, radar, agyroscopic sensor inside a computer held or worn by the user, or thelike. Camera 240 may be used to track physical eye movements of a userof client computer 200.

GPS transceiver 258 can determine the physical coordinates of clientcomputer 200 on the surface of the Earth, which typically outputs alocation as latitude and longitude values. GPS transceiver 258 can alsoemploy other geo-positioning mechanisms, including, but not limited to,triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference(E-OTD), Cell Identifier (CI), Service Area Identifier (SAI), EnhancedTiming Advance (ETA), Base Station Subsystem (BSS), or the like, tofurther determine the physical location of client computer 200 on thesurface of the Earth. It is understood that under different conditions,GPS transceiver 258 can determine a physical location for clientcomputer 200. In at least one embodiment, however, client computer 200may, through other components, provide other information that may beemployed to determine a physical location of the client computer,including for example, a Media Access Control (MAC) address, IP address,and the like.

Human interface components can be peripheral devices that are physicallyseparate from client computer 200, allowing for remote input and/oroutput to client computer 200. For example, information routed asdescribed here through human interface components such as display 250 orkeyboard 252 can instead be routed through network interface 232 toappropriate human interface components located remotely. Examples ofhuman interface peripheral components that may be remote include, butare not limited to, audio devices, pointing devices, keypads, displays,cameras, projectors, and the like. These peripheral components maycommunicate over a Pico Network such as Bluetooth™, Zigbee™ and thelike. One non-limiting example of a client computer with such peripheralhuman interface components is a wearable computer, which might include aremote pico projector along with one or more cameras that remotelycommunicate with a separately located client computer to sense a user'sgestures toward portions of an image projected by the pico projectoronto a reflected surface such as a wall or the user's hand.

A client computer may include web browser application 226 that may beconfigured to receive and to send web pages, web-based messages,graphics, text, multimedia, and the like. The client computer's browserapplication may employ virtually any programming language, including awireless application protocol messages (WAP), and the like. In at leastone embodiment, the browser application is enabled to employ HandheldDevice Markup Language (HDML), Wireless Markup Language (WML),WMLScript, JavaScript, Standard Generalized Markup Language (SGML),HyperText Markup Language (HTML), eXtensible Markup Language (XML),HTMLS, and the like. Web browser 226 may be used to configure routes onmanagement platform server computer 116, as discussed below inconjunction with FIG. 3. For example, a user may operate web browserapplication 226 in order to enable a first group of node computers tocommunicate with the second group of node computers through one or moregateway computers or relay computers.

Memory 204 may include RAM, ROM, and/or other types of memory. Memory204 illustrates an example of computer-readable storage media (devices)for storage of information such as computer-readable instructions, datastructures, program modules or other data. Memory 204 may store BIOS 208for controlling low-level operation of client computer 200. The memorymay also store operating system 206 for controlling the operation ofclient computer 200. It will be appreciated that this component mayinclude a general-purpose operating system such as a version of UNIX, orLINUX™, or a specialized client computer communication operating systemsuch as Windows Phone™, or the Symbian® operating system. The operatingsystem may include, or interface with a Java virtual machine module thatenables control of hardware components and/or operating systemoperations via Java application programs.

Memory 204 may further include one or more data storage 210, which canbe utilized by client computer 200 to store, among other things,applications 220 and/or other data. For example, data storage 210 mayalso be employed to store information that describes variouscapabilities of client computer 200. The information may then beprovided to another device or computer based on any of a variety ofevents, including being sent as part of a header during a communication,sent upon request, or the like. Data storage 210 may also be employed tostore social networking information including address books, buddylists, aliases, user profile information, or the like. Data storage 210may further include program code, data, algorithms, and the like, foruse by a processor, such as processor 202 to execute and performactions. In one embodiment, at least some of data storage 210 might alsobe stored on another component of client computer 200, including, butnot limited to, non-transitory processor-readable removable storagedevice 236, processor-readable stationary storage device 234, or evenexternal to the client computer.

Applications 220 may include computer executable instructions which,when executed by client computer 200, transmit, receive, and/orotherwise process instructions and data. Applications 220 may include,for example, web browser 226. Other examples of application programsinclude calendars, search programs, email client applications, IMapplications, SMS applications, Voice Over Internet Protocol (VOIP)applications, contact managers, task managers, transcoders, databaseprograms, word processing programs, security applications, spreadsheetprograms, games, search programs, and so forth.

Additionally, in one or more embodiments (not shown in the figures),client computer 200 may include an embedded logic hardware deviceinstead of a CPU, such as, an Application Specific Integrated Circuit(ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic(PAL), or the like, or combination thereof. The embedded logic hardwaredevice may directly execute its embedded logic to perform actions. Also,in one or more embodiments (not shown in the figures), the networkcomputer may include a hardware microcontroller instead of a CPU. In atleast one embodiment, the microcontroller may directly execute its ownembedded logic to perform actions and access its own internal memory andits own external Input and Output Interfaces (e.g., hardware pins and/orwireless transceivers) to perform actions, such as System On a Chip(SOC), or the like.

Illustrative Network Computer

FIG. 3 shows one embodiment of network computer 300 that may be includedin a system implementing the invention. Network computer 300 may includemany more or less components than those shown in FIG. 3. However, thecomponents shown are sufficient to disclose an illustrative embodimentfor practicing these innovations. Network computer 300 may represent,for example, one embodiment of one or more of management platform servercomputer 116, gateway computers 118, relay computers 120, or one or morenode computers 122 of FIG. 1.

As shown in the figure, network computer 300 includes a processor 302 incommunication with a memory 304 via a bus 328. Network computer 300 alsoincludes a power supply 330, network interface 332, audio interface 356,display 350, keyboard 352, input/output interface 338,processor-readable stationary storage device 334, and processor-readableremovable storage device 336. Power supply 330 provides power to networkcomputer 300.

In at least one of the various embodiments, processor 302 may includeone or more separate hardware processors that are arranged to performone or more specific task or actions. Also, in some embodiments, the oneor more hardware processors comprising processor 302 may be the sameprocessor. In some embodiments, the one or more hardware processorscomprising processor 302 may be the included in the same networkcomputer. In some embodiments, one or more of the one or more hardwareprocessors comprising processor 302 may be included in different networkcomputers.

Network interface 332 includes circuitry for coupling network computer300 to one or more networks, and is constructed for use with one or morecommunication protocols and technologies including, but not limited to,protocols and technologies that implement any portion of the OpenSystems Interconnection model (OSI model), global system for mobilecommunication (GSM), code division multiple access (CDMA), time divisionmultiple access (TDMA), user datagram protocol (UDP), transmissioncontrol protocol/Internet protocol (TCP/IP), Short Message Service(SMS), Multimedia Messaging Service (MMS), general packet radio service(GPRS), WAP, ultra wide band (UWB), IEEE 802.16 WorldwideInteroperability for Microwave Access (WiMax), Session InitiationProtocol/Real-time Transport Protocol (SIP/RTP), or any of a variety ofother wired and wireless communication protocols. Network interface 332is sometimes known as a transceiver, transceiving device, or networkinterface card (NIC). Network computer 300 may optionally communicatewith a base station (not shown), or directly with another computer.

Audio interface 356 is arranged to produce and receive audio signalssuch as the sound of a human voice. For example, audio interface 356 maybe coupled to a speaker and microphone (not shown) to enabletelecommunication with others and/or generate an audio acknowledgementfor some action. A microphone in audio interface 356 can also be usedfor input to or control of network computer 300, for example, usingvoice recognition.

Display 350 may be a liquid crystal display (LCD), gas plasma,electronic ink, light emitting diode (LED), Organic LED (OLED) or anyother type of light reflective or light transmissive display that can beused with a computer. Display 350 may be a handheld projector or picoprojector capable of projecting an image on a wall or other object.

Network computer 300 may also comprise input/output interface 338 forcommunicating with external devices or computers not shown in FIG. 3.Input/output interface 338 can utilize one or more wired or wirelesscommunication technologies, such as USB™, Firewire™, WiFi, WiMax,Thunderbolt™, Infrared, Bluetooth™, Zigbee™, serial port, parallel port,and the like.

GPS transceiver 362 can determine the physical coordinates of networkcomputer 300 on the surface of the Earth, which typically outputs alocation as latitude and longitude values. GPS transceiver 362 can alsoemploy other geo-positioning mechanisms, including, but not limited to,triangulation, assisted GPS (AGPS), Enhanced Observed Time Difference(E-OTD), Cell Identifier (CI), Service Area Identifier (SAI), EnhancedTiming Advance (ETA), Base Station Subsystem (BSS), or the like, tofurther determine the physical location of network computer 300 on thesurface of the Earth. It is understood that under different conditions,GPS transceiver 362 can determine a physical location for networkcomputer 300. In at least one embodiment, however, network computer 300may, through other components, provide other information that may beemployed to determine a physical location of the client computer,including for example, a Media Access Control (MAC) address, IP address,and the like.

Human interface components can be physically separate from networkcomputer 300, allowing for remote input and/or output to networkcomputer 300. For example, information routed as described here throughhuman interface components such as display 350 or keyboard 352 caninstead be routed through the network interface 332 to appropriate humaninterface components located elsewhere on the network. Human interfacecomponents include any component that allows the computer to take inputfrom, or send output to, a human user of a computer. Accordingly,pointing devices such as mice, styluses, track balls, or the like, maycommunicate through pointing device interface 358 to receive user input.

Memory 304 may include Random Access Memory (RAM), Read-Only Memory(ROM), and/or other types of memory. Memory 304 illustrates an exampleof computer-readable storage media (devices) for storage of informationsuch as computer-readable instructions, data structures, program modulesor other data. Memory 304 stores a basic input/output system (BIOS) 308for controlling low-level operation of network computer 300. The memoryalso stores an operating system 306 for controlling the operation ofnetwork computer 300. It will be appreciated that this component mayinclude a general-purpose operating system such as a version of UNIX, orLINUX™, or a specialized operating system such as MicrosoftCorporation's Windows® operating system, or the Apple Corporation's IOS®operating system. The operating system may include, or interface with aJava virtual machine module that enables control of hardware componentsand/or operating system operations via Java application programs.Likewise, other runtime environments may be included.

Memory 304 may further include one or more data storage 310, which canbe utilized by network computer 300 to store, among other things,applications 320 and/or other data. For example, data storage 310 mayalso be employed to store information that describes variouscapabilities of network computer 300. The information may then beprovided to another device or computer based on any of a variety ofevents, including being sent as part of a header during a communication,sent upon request, or the like. Data storage 410 may also be employed tostore social networking information including address books, buddylists, aliases, user profile information, or the like. Data storage 310may further include program code, instructions, data, algorithms, andthe like, for use by a processor, such as processor 302 to execute andperform actions such as those actions described below. In oneembodiment, at least some of data storage 310 might also be stored onanother component of network computer 300, including, but not limitedto, non-transitory media inside processor-readable removable storagedevice 336, processor-readable stationary storage device 334, or anyother computer-readable storage device within network computer 300, oreven external to network computer 300.

Data storage 310 may include, for example, overlay network information312, gateway ID information 314, or the like. Overlay networkinformation 312 may contain policy data defining which gateways, relays,or node computers are allowed to communicate with each other as well asthe physical network routes that may be available. In one embodiment,overlay network information 312 may be generated and stored onmanagement platform servers, such as, management platform servercomputer 116 before being distributed to gateway computers 118 and relaycomputers 120.

Data storage 310 may also include gateway identifier information 314that may include information for identifying the gateway computerendpoints of for connection routes. A network address (e.g., IP addressand port) for a given gateway computer may be discovered by a relaycomputer when the gateway computer initiates a connection to the relaycomputer. In scenarios when a gateway computer is located in a privatenetwork a public facing network address for that gateway computer maynot be knowable unless the gateway computer initiates a connectionoutside of the private network.

Applications 320 may include computer executable instructions which,when executed by network computer 300, transmit, receive, and/orotherwise process messages (e.g., SMS, Multimedia Messaging Service(MMS), Instant Message (IM), email, and/or other messages), audio,video, and enable telecommunication with another user of another mobilecomputer. Other examples of application programs include calendars,search programs, email client applications, IM applications, SMSapplications, Voice Over Internet Protocol (VOIP) applications, contactmanagers, task managers, transcoders, database programs, word processingprograms, security applications, spreadsheet programs, games, searchprograms, and so forth. Applications 320 may include overlay networkengine 322, management platform engine 324, relay engine 326, or gatewayengine 327 which may be enabled to perform actions further describedbelow. In at least one of the various embodiments, one or more of theapplications or portions of applications may be implemented as modulesor components of another application. Further, in one or more of thevarious embodiments, applications or portions of applications may beimplemented as operating system extensions, modules, plugins, or thelike.

In at least one of the various embodiments, applications, such as,operating system 306, overlay network engine 322, management platformengine 324, relay engine 326, gateway engine 327, or the like, may bearranged to employ geo-location information to select one or morelocalization features, such as, time zones, languages, currencies,calendar formatting, or the like. Localization features may be used wheninterpreting network traffic, interpreting node computer activity,monitoring or logging application activity, user-interfaces, reports, aswell as internal processes and/or databases. In at least one of thevarious embodiments, geo-location information used for selectinglocalization information may be provided by GPS 362. Also, in someembodiments, geolocation information may include information providedusing one or more geolocation protocols over the networks, such as,wireless network 108 and/or network 110.

Furthermore, in at least one of the various embodiments, overlay networkengine 322, management platform engine 324, relay engine 326, gatewayengine 327, or the like, may be operative in a cloud-based computingenvironment. In at least one of the various embodiments, theseapplications, and others, that comprise the management platform may beexecuting within virtual machines and/or virtual servers that may bemanaged in a cloud-based based computing environment. In at least one ofthe various embodiments, in this context the applications may flow fromone physical network computer within the cloud-based environment toanother depending on performance and scaling considerationsautomatically managed by the cloud computing environment. Likewise, inat least one of the various embodiments, virtual machines and/or virtualservers dedicated to overlay network engine 322, management platformengine 324, relay engine 326, gateway engine 327, or the like, may beprovisioned and de-commissioned automatically. Also, in at least one ofthe various embodiments, overlay network information 312, gatewayidentifier information 314, or the like, may located in virtual serversrunning in a cloud-based computing environment rather than being tied toone or more specific physical network computers. In some embodiments,various applications, data storage, or the like, may be operative in oneor more container computers executing in a container computingenvironment.

Further, network computer 300 may also comprise hardware security module(HSM) 360 for providing additional tamper resistant safeguards forgenerating, storing and/or using security/cryptographic information suchas, keys, digital certificates, passwords, passphrases, two-factorauthentication information, or the like. In some embodiments, hardwaresecurity module may be employ to support one or more standard public keyinfrastructures (PKI), and may be employed to generate, manage, and/orstore keys pairs, or the like. In some embodiments, HSM 360 may be astand-alone network computer, in other cases, HSM 360 may be arranged asa hardware card that may be installed in a network computer.

Additionally, in one or more embodiments (not shown in the figures),network computer 300 may include an embedded logic hardware deviceinstead of a CPU, such as, an Application Specific Integrated Circuit(ASIC), Field Programmable Gate Array (FPGA), Programmable Array Logic(PAL), or the like, or combination thereof. The embedded logic hardwaredevice may directly execute its embedded logic to perform actions. Also,in one or more embodiments (not shown in the figures), the networkcomputer may include a hardware microcontroller instead of a CPU. In atleast one embodiment, the microcontroller may directly execute its ownembedded logic to perform actions and access its own internal memory andits own external Input and Output Interfaces (e.g., hardware pins and/orwireless transceivers) to perform actions, such as System On a Chip(SOC), or the like.

Illustrative Logical System Architecture

FIG. 4 illustrates a logical schematic of network 400 that includesoverlay networks, node computers, gateway computers, relay computer inaccordance with at least one of the various embodiments. Network 400 isarranged to include gateway computers, such as, gateway computers412-418. Gateway computers may be disposed between one or more nodecomputers and the underlying physical network infrastructure. In atleast one of the various embodiments, the gateway computers may bearranged such that they isolate node computers, such as, node computers402-410 from the physical network used to interconnect them. Also, inthis example, management platform server computer 440 represents one ormore management platform servers that may be assumed to be arranged tocommunicate over one or more networks with relay computers and gatewaycomputers that comprise network 400. In one or more of the variousembodiments, among other things, management platform server 440 may bearranged to manage the configuration or distribution of policyinformation.

In this example, physical networks, such as, physical network 420 a,physical network 420 b, a public network 432 provide an underlyingphysical network comprising network 400. In this example, node computer404 is isolated from physical network 420 a by gateway 414.

Also, in one or more of the various embodiments, private networks, suchas, private network 426, private network 428, or private network 430 mayrepresent separate or isolated networks that may be configured toprevent computers them from being visible or directly accessible fromoutside each of the private networks.

In some embodiments, gateway computers may be arranged to communicatewith one or more relay computers, such as, relay computer 434 viaanother network, such as, network 432. In some embodiments, relaycomputer 434 may be arranged to have a network address that may bevisible from computers that may be part of other networks, includingprivate networks, such as, private network 420 a and private network 420b, or the like.

Accordingly, in at least one of the various embodiments, the gatewaycomputers may be configured to provide or enforce one or more overlaynetworks in network 400. In this example, for some embodiments, overlaynetwork 422 enables node computer 406 and node computer 408 to “see”each other on the network; communication from node computer 406 to nodecomputer 408 may be routed through gateway computer 416 to network 432to relay 434 to gateway computer 418; and the communication may then berouted from gateway computer 418 to node 408 over private network 420 b.From the point-of-view of node computer 406 and node computer 408 thecommunication appears to go directly over overlay network 422. Inactuality the communication will be routed from node 406 to gatewaycomputer 416 to relay 432 to gateway computer 418.

Likewise, in this example, network 400 may be arranged such that nodecomputer 402, node computer 406, and node computer 410 communicate overoverlay network 424. As described above, in at least one of the variousembodiments, the communication among/between the nodes on overlaynetwork 424 may be routed through relay 434 and two or more of thegateway computers.

In at least one of the various embodiments, the gateway computers may beconfigured with one or more rule-based policies that determine access orrestrictions for network communication on the networks. The particularrules or restrictions associated with how communication information(e.g., network packets) should be routed through the mesh network may beestablished by a management platform computer, such as managementplatform server computer 440, or the like. Configuration information maybe pushed (e.g., router tables) to each gateway computer to define theoverlay networks, if any, as well other restrictions that may beapplicable for one or more networks.

In at least one of the various embodiments, gateway computers may bearranged to include an explicit list of computer addresses/identitiesthat are allowed to communicate with the gateway computer. Accordingly,if a node computer, such as, node computer 410 is in gateway computer418's list of allowed computers (e.g., a whitelist) it may be enabled toinitiate communication over the mesh network through gateway computer418. Conversely, node computers, or any other computer for that matter,not in a gateway computer's whitelist may be denied access to thatgateway computer and the mesh network. Though, in some embodiments, anode computer may be allowed to access one or more particular gatewaycomputers and denied accessed to others. In at least one of the variousembodiments, a management platform computer, such as, managementplatform server computer 440, may be arranged to manage and distributethe whitelists to the one or more gateway computers.

In at least one of the various embodiments, by placing gateway computersbetween physical networks (e.g., private network 420 a or privatenetwork 420 b) and the node computers, the configuration or definitionof one or more overlay networks may be accomplished without requiringthe individual node computers to be reconfigured. Further, in at leastone of the various embodiments, gateway computers may comprise securityhardened computers that provide various routing, security and/orcryptography features to help secure the one or more networks.Otherwise, in at least one of the various embodiments, the network maybe reliant on the security features of the node computers themselveswhich may be non-existent or very limited.

In at least one of the various embodiments, overlay networks may beenforced by using an overlay whitelist that defines the endpoints (e.g.,node computer, gateway computers, relays, or the like) that may beaccessed from other members of the overlay network. Accordingly, in atleast one of the various embodiments, the computers on a given overlaynetwork may be included on the overlay network whitelist. Likewise, inat least one of the various embodiments, computers absent from theoverlay network may be omitted or excluded from the overlay networkwhitelist. Further, in at least one of the various embodiments, acomputer may be included on more than one overlay network whitelistenabling it to be part of multiple overlay networks. In at least one ofthe various embodiments, management platform computer 440 may bearranged to manage and distribute the overlay whitelists to each gatewaycomputer comprising a mesh network.

In some embodiments, computers in different networks may be unable toidentify or access each other because this their local networks areusing separate (perhaps conflicting) network address namespaces. Forexample, gateway computer 418, and consequently, node computers 408 and410, cannot be accessed from outside of the private network 420 bwithout gateway computer 418 first initiating a connection outside ofprivate network 420 b. This may be true even if a public network addressassociated with private network 420 b is known because the networkaddress of node computers in private networks, such as, private network420 b are not generally available to computers outside of the sameprivate networks.

In some embodiments, relay computers, such as relay computer 434, may beassociated with network addresses that are accessible from computers inone or more private or one or more public networks, in some cases, thismay include the public Internet. In one embodiment, a node computer mayrequest that a gateway computer initiate a connection to another nodecomputer via another gateway computer that are located in anothernetwork. However, if neither gateway computer can see the other, becausethey are both located in separate private networks, one or more relaycomputers, such as, relay computer 434 may be employed to bridge thenetworks to enable node computers in one network to reach node computersin another network.

In one embodiment, a gateway computer may be arranged to send an initialconnection request packet to a relay computer. In some embodiments, theinitial packet may include at least a gateway identifier (GID) of thesource gateway computer and a GID of the target gateway computer. Therelay may authorize or facilitate communication between the sourcegateway computer and the target gateway computer based on policyinformation received from management platform server 440. Onceauthorized, relay 434 may participate in the establishment andmaintenance of the connection with the target gateway computer byforwarding the “I1” initiator packet to the target gateway computer,while continuing to forward control packets between the source andtarget gateway computers.

In one or more of the various embodiments, control packets may includehandshake packets such as initiator 1, responder 1, initiator 2, andresponder2, or the like, to established connections between gatewaycomputers. Other control packets may include keep-alive packets that aresent from a gateway computer to a relay computer.

For example, gateway computer 418 may send an “I1” packet to relay 434over network 432 where the “I1” packet includes a gateway identifier(GID) associated with gateway computer 418 as the source and a GIDidentifying gateway computer 414 as the target. If relay 434 hasestablished a connections with gateway computer 414, relay 434 will havealready obtained and indexed information, such as, ingress identifier touse for routing packets to gateway computer 414, such as, a securityparameter index (SPI) associated with the connection to gateway 414, aswell as, a network address (or other tuple information) for accessinggateway 414. In some embodiments, relay 434 may obtain information fromnetwork packets sent by gateway 418 to obtain information foridentifying or associate network packets or network flows with gateway418, such as, an SPI associated with the connection to gateway 418, aswell as, a network address (or other tuple information) for accessinggateway 418. If network addresses of both gateway computers are knownand indexed by relay 434, relay 434 may be arranged to employ thisinformation to forward handshake packets between them. However, in thisexample, if relay 434 has not received an initialization packet fromgateway computer 414, relay 434 may be arranged to drop the “I1”request. In one or more of the various embodiments, relay 434 maycontinue dropping request to communicate with gateway 414 until relay434 has obtained and indexed gateway computer 414's identificationinformation (e.g., ingress identifier, network address information, orthe like).

In one or more of the various embodiments, a gateway computer, such as,gateway computer 418, or the like, may broadcast requests to establish aconnection to a target gateway computer to multiple relays. For example,gateway computer 418 may broadcast an “I1” packet to two or more relays.This broadcast technique performs the process discussed above to attemptto establish a connection with the two or more relays independently andin parallel. In one embodiment, the relay computer selected by thegateway computer may be the first relay computer to complete thehandshake process. Further, in some embodiments, additional criteria orconditions may be applied to select a relay computer from among two ormore available relay computers.

In one embodiment, management platform servers, such as, managementplatform server 440 may be arranged to enable users or operators tocreate relay policy rules. For example, a relay policy rule may definethat gateway computer 418 may communicate with gateway computer 414 viarelay 434. In some embodiments, relay policy rules may be defined interms of groups of gateway computers or groups of relays.

In one or more of the various embodiments, if connections may be routedthrough one of a plurality of relays, these connections may be activelybalanced to improve throughput, latency, and cost efficiency. In oneembodiment, an overburdened relay may simply drop a connection. Forexample, if gateway computer 418 is connected to gateway computer 414through relay 434, and relay 434 drops the connection, gateway computer418 may attempt to use another relay computer allowed by the currentpolicy rules. Additionally or alternatively, relays that areoverburdened with connections may artificially delay processing newinitialization packets to enable faster responding relay computers toestablish connections with the requesting gateway computers. Forexample, before forwarding an “I1” packet on to a destination gatewaycomputer, an overburdened relay may insert a delay that causes the routethrough that particular relay to appear to be slow, making it lesslikely that a route using the overburdened relay will be chosen.

In one or more of the various embodiments, rebalancing may also beachieved by arranging relay computers that have excess capacity toactively prioritize new connections. For example, if relay 434determines that an above average number of keep-alive packets are beingprocessed, as opposed to connections transmitting actual data, relay 434may prioritize participating in new connections. For example, if relay434 receives a new “I1” initialization packet, it may prioritizeprocessing the packet above other system functions, thereby increasingthe chance that it will have the lowest latency. Similarly, in someembodiments, a relay computer that has an above average number ofkeep-alive packets may also prioritize keeping alive the connections itis currently participating in.

In one or more of the various embodiments, while gateway computers maybe stationary on a network, in that they maintain the same networkaddress indefinitely, the network address for a gateway computer maychange from time to time. For example, a gateway computer may be movedto a different location, e.g. to another building on a corporate campusthat is associated with a different range of network addresses.Similarly, a gateway that is a mobile device such as a smart phone maypass between cell towers or access points, each of which may beassociated with a different network addresses. In one or more of thevarious embodiments, gateway computers may also experience a change innetwork address if the network changes, e.g. if a new internet serviceprovider (ISP) is introduced. However it happens, if a network addressassociated with a gateway computer changes, any existing connectionsusing that network address will be dropped. However, because identitybased networking does not rely on a host's location as identity, theconnection can be seamlessly re-established if management platformserver 440 discovers the change and broadcasts the new network addressfor the gateway computer. For example, if gateway computer 416determines that its network address has changed, it will notify itsassociated management platform server of the change. In one or more ofthe various embodiments, the management platform server may thenbroadcast updated policies that include rules for the new networkaddress. Accordingly, in one or more of the various embodiments, anexisting connection between gateway computer 416 and gateway computer412 through relay 434 may continue once relay 434 receives an updatedpolicy from management platform server 440.

In one or more of the various embodiments, gateway 416 may attempt toinform gateway 412 of its new network address, via relay 434.Accordingly, in some embodiments, relay 434 may be arranged to detectthis new network address mapping and update itself accordingly. The peergateway 412 may also get the new network address, but since thecommunication between the two gateways is being relayed, gateway 412does not need to do anything differently.

In one or more of the various embodiments, connections between gatewaycomputers may be maintained with or without connection to the managementplatform server. In some embodiments, gateway computers may be arrangedto inform each other of their own address updates, for activeconnections between gateway computers. In contrast, new connections,will need to obtain the latest reachable address from the managementplatform server.

It is also possible for a device, such as one of nodes 402, 404, 406,408, or 410, to be moved to a different gateway computer. In thisscenario, management platform server 440 has to be notified of the newconfiguration before the node is to work again properly. For example, ifnode 410 were moved from private network 420 b to private network 420 a,management platform server 440 could be informed, either manually orautomatically, and then update relevant relays with new policies. Forexample, the relay policy may include a rule that prescribes thatgateway 416 may be relayed to gateway 412. Accordingly, in someembodiments, relay computers can enforce relay policy without seeinginside the connections between gateways. Thus, in some embodiments,relays may be arranged to be unaware of the nodes or node policies. Forexample, node 410 is not known to the relay; it works with the gatewaycomputers.

Existing connections may time-out or reset automatically, when it isdiscovered that endpoint no longer exists at the network address theconnection is directed towards. Once a connection has timed-out orreset, a new connection may be initiated and the connection betweenendpoints may continue uninterrupted.

FIG. 5 illustrates a logical representation of system 500 forcommunicating in a network in accordance with at least one of thevarious embodiments. In at least one of the various embodiments,communications that are processed on a gateway computer may comprisevarious logical layers that may comprise a functional networkcommunication stack. In at least one of the various embodiments, acommunication on one gateway computer, such as, communication 502 may bearranged such that an application layer, such as, application layer 504may perform actions that include communication; next at layer 506, oneor more standard network protocols APIs (TCP in this example) may beemployed; at layer 508 one or more special actions may be performed tosupport the overlay networks. And, before the communication is sent out,the lower level layers, such as, layer 510 (IP layer in this example)may be applied.

In at least one of the various embodiments, gateway computers may bearranged to substitute their GID for use as a network address by higherlayers such as application layer 504 and TCP layer 506. The GID may bearranged to be compatible with the native data structures that may beused to represent actual network addresses. Accordingly, in at least oneof the various embodiments, application level networking API's thataccept network address data structures as parameters may be enabled toaccept GID instead. For example, in some embodiments, an internetaddress may be represented using a 32-bit value. Thus, in suchembodiments, the GID may be a 32-bit number, making it size compatiblewith an ordinary network address value.

In at least one of the various embodiments, at the gateway layer, layer508 in FIG. 5, the GID of the source gateway and/or the target gatewayare mapped to an actual network address. In at least one of the variousembodiments, component 512 may represent components that are arranged tomap GIDs to network addresses, and component 514 may representcomponents that are arranged to map from a network address to a GID.

In at least one of the various embodiments, since the GIDs may be mappedto an actual network address, a network layer, such as IP layer 510 maygenerate the appropriate network protocol information for thecommunication. Accordingly, in at least one of the various embodiments,network path 516 may be employed to communicate the communicationnetwork packets to its next destination.

In at least one of the various embodiments, communication 518 representsthe received version of communication 502. The network protocol layer(IP layer 520) accepts the communication over the network; gateway layer522 employs component 524 and component 526 to map network addresses toGIDs; TCP layer 528 performs higher level network protocol actions usingthe GID in place of the network address; and application layer 530employs the payload of the communication to perform application specificactions based on the actual contents of the payload.

FIG. 6 illustrates a portion of policy 600 for defining connectionroutes allowed between pairs of gateway computers. Specifically, dataobject 502 lists pairs of gateway computers that are defined asauthorized to connect with each other. In one or more of the variousembodiments, data object 502 includes column 504, which lists publickeys associated with one of two gateway computers authorized to connectwith each other, while column 506 lists public keys associated with thecorresponding gateway computers. For example, the first row of table 502indicates that the gateway computer having the public key that beginswith “MIICWg” may connect with the gateway computer having the publickey that begins with “QpEzw0”. Similarly, the second row indicates thatthe gateway computer with the public key beginning with “MIICWg” mayalso connect with the gateway computer having the public key that beginswith “OzXeYr”.

In one embodiment, a network policy provided by a management platformserver may include a list of pairs of gateway computers that areauthorized to connect with each other. In one embodiment the list ofpairs is defined by a list of pairs of gateway identifiers (GIDs). Inone or more of the various embodiments, GIDs may be created by applyinga hash function to a public key or other shared secret.

For example, data object 608 includes a list of pairs of GIDs thatdefine which gateway computers may be authorized to connect with eachother. Similar to data object 602, data object 608 includes column 610which lists GIDs for one of two gateway computers allowed to connect,while column 612 lists GIDs for the other of the two gateway computersallowed to connect. In one embodiment, data object 608 comprises anetwork policy that is distributed by a management platform server toeach of the relay computers and gateway computers in associated with anoverlay network.

FIG. 7 illustrates connection information 700 for accumulating at leastsome of the information that enables overlay network identity-basedrelay between gateway computers. In one or more of the variousembodiments, data object 702 includes ingress identifiers columns 704and 710, GID columns 706 and 712, and gateway computer network addresscolumns 708 and 714. In one or more of the various embodiments, dataobject 702 lists pairs of gateway computers that are allowed to connectto one another, as defined by a policy received from a managementplatform server.

In one or more of the various embodiments, columns 704, 706, and 708 maybe associated with a first gateway computer in a given pair of gatewaycomputers (e.g., Gateway A), while columns 710, 712, and 714 may beassociated with a second gateway computer (Gateway B) in the given pairof gateway computers. For example, in some embodiments, row 716 definesthat the gateway computer with GID “0x23fd7a39153cab91” may connect tothe gateway computer with GID “0x354cb98e4fa65002”.

As discussed above, the ingress identifier may be used to distinguishdifferent network packet streams (network flows). For example, in someembodiments, connections having different Encapsulated SecurityProtocols (ESPs) as part of an Internet Protocol security (IPsec)protocol may be identified using their security parameter index as aningress identifier. In one embodiment, each gateway computer may bearranged to select a random number as an ingress identifier (e.g., SPI),and include it within packets communicated during an initial handshake.In one embodiment, a relay computer may observe the ingress identifiervalues, associate them with a GID and an network address, and insertthem into data object 702. In one embodiment, ingress identifier valuesare used as indices into data object 702 when routing data over aconnection, Accordingly, in some embodiments, an ingress identifier maybe used to lookup connection route information for the target gatewaycomputer.

In one embodiment, ingress identifiers may be SPI values are 32 bits,ranging from 0 to approximately 4,294,967,295, and while this mayprovide a large number of potential values compared to a number ofconnections typically maintained by a relay, it is still possible forcollisions to occur—i.e. a first gateway computer and a second gatewaycomputer (or a first gateway computer and a third gateway computer) mayrandomly select the same ingress identifier while trying to connect tothe same relay, even if the first and second gateway computer are not incommunication with each other.

In one embodiment, a relay computer may be arranged to discoverduplicate ingress identifiers when the relay computer processes ahandshake packet, such as, an “I1” packet. In this example, for one ormore of the various embodiments, if a duplicate ingress identifier valueis found in data object 702, the handshake packets may be dropped (e.g.not responded to). In one embodiment, the relay may also send an errorcode or other message to the gateway computer indicating a duplicateingress identifier as the cause of the error. Upon receiving anindication of the error, or upon timing out after re-trying “I1” packetswith the same ingress identifier a defined number of times, the gatewaycomputer attempting to use an ingress identifier that is already in dataobject 702 may be arranged to generate a new ingress identifier and tryagain to establish a connection with a relay computer.

In one embodiment, columns 706 and 712 include gateway identities(GIDs). In one or more of the various embodiments, GIDs may becryptographic hashes of a public key associated with the correspondinggateway computer, similar to columns 710 and 612 as described above inconjunction with FIG. 6.

In one or more of the various embodiments, columns 708 and 714 containnetwork address information associated with gateway computers, such as,IP addresses and ports. In one embodiment, the gateway computers mayexist behind a NAT on a private network and have been assigned a privateIP address (i.e. an IP address that is not generally addressable fromhosts on the public internet). However, the IP addresses stored incolumns 708 and 714 may be the IP addresses of the NAT device that iscreating the private network, while the ports stored in columns 708 and714 may be mapped by the NAT device to a particular host on the privatenetwork.

Notably absent from data object 702 are shared secret keys or otherartifacts of the connection request handshake that might be used todecrypt data packets as they are forwarded to gateway computer. During ahandshake exchange, gateway computer endpoints generate shared secretkeys using a cryptographic algorithm such as Diffie-Hellman. Thisprevents a man-in-the-middle, such as a relay computer or other networkcomputer, from determining the secret key. Thus once a connection isestablished between two gateway computers, a relay forwards packets,without decrypting their contents, based on the ingress identifiers ofincoming packets and columns 708 and 714 of data object 702 to locatethe actual destination network address that may be associated withgateway computers. In this way, scalability or performance may beimproved by avoiding processor intensive decryption and re-encryptionoperations at the relay computer.

Further, in some embodiments, the initial handshake process used toestablish links between relays and gateway computers may be stateless.Accordingly, in some embodiments, link state information is not storedat the relay computers or target gateway computers until an initialexchange of secrets is verified and authenticated. For example, a firstcontrol packet may include secrets from the source gateway computer andthe second control packet sent in response from the target gatewaycomputer may include secrets associated with the target gatewaycomputer. But, at this point in the handshake neither endpoint isstoring connection state. Accordingly, malicious attacks that attempt todisrupt gateway computers or relays by consuming resource by creatinghalf-open connections (e.g., SYN flood style attacks, or the like) maybe prevented because there is no connection related state is storeduntil secrets exchanged between the target and source are verified andauthenticated.

FIG. 8 illustrates a logical representation of network packet 800 andnetwork packet 806. Network packet 800 is an example of a standardscompatible network packet that may be used to communicate betweengateway computers or relay computers. In this example, the networkpacket represents the well-known structure of an IPSEC packet. Accordingto the IPSEC protocol, the fields for an IPSEC header comprise thefields in header 802. One of those fields, 804, is suitable for storingan SPI field of an IPSEC header. Further, in one or more of the variousembodiments, Encapsulating Security Payload (ESP) network packets, suchas, network packet 806 which is also part of the IPSEC protocol may beused to establish connections or communicate between gateway computersor relay computers.

One of ordinary skill in the art will appreciate and understand thevarious fields of an IPSEC protocol network packets. Accordingly, it isin the interest clarity and brevity that all of the fields are notfurther explained here.

Generalized Operations

FIGS. 9-10 represent the generalized operation of overlay networkidentity-based relay in accordance with at least one of the variousembodiments. In at least one of the various embodiments, processes 900and 1000 described in conjunction with FIGS. 9-10 may be implemented byand/or executed on one or more processors of a relay computer, a gatewaycomputer, and/or a conductor, such as network computer 300 of FIG. 3. Inother embodiments, these processes, or portions thereof, may beimplemented by and/or executed on one or more processors of a pluralityof network computers, such as network computer 300 of FIG. 3. In yetother embodiments, these processes, or portions thereof, may beimplemented by and/or executed on one or more virtualized computers,such as, those in a cloud-based environment. However, embodiments arenot so limited and various combinations of network computers, clientcomputers, or the like may be utilized. Further, in at least one of thevarious embodiments, the processes described in conjunction with FIGS.9-10 may be used for overlay network identity-based relay in accordancewith at least one of the various embodiments and/or architectures suchas those described in conjunction with FIGS. 4-8. Further, in at leastone of the various embodiments, some or all of the action performed byprocesses 900 and 1000 may be executed in part by overlay network engine322, management platform engine 324, relay engine 326, gateway engine327, or the like, or combination thereof.

FIG. 9 illustrates an overview flowchart of process 900 for overlaynetwork identity-based relay in accordance with at least one of thevarious embodiments. In one embodiment, process 900 may be implementedby relay computers 120 of FIG. 1, or the like. After a start block, atblock 902, in at least one of the various embodiments, overlay networkpolicy may be obtained from a management platform server, such as,management platform server computer 116 of FIG. 1. In one or more of thevarious embodiments, the policy may define allowed routes betweengateway computers, e.g. a whitelist of allowed connections. In oneembodiment the pairs of gateway computers are denoted by pairs ofgateway identifiers (GIDs). A GID may, in one embodiment, comprise a 128bit cryptographic hash of a public keys associated with a gatewaycomputer. In one embodiment, a relay computer instantiating process 900may be arranged to have one or more network interfaces that may beassigned network addresses that are addressable or otherwise accessiblefrom two or more networks. For example, a relay computer supporting twoor more gateway computers located on separate networks may be configuredsuch that the relay computer may be accessible by the two or moregateway computer.

At decision block 904, in one or more of the various embodiments, if asource gateway computer is ready to initiate communication with a targetgateway computer, control may flow to block 906; otherwise control mayloop back to decision block 904. For example, in one or more of thevarious embodiments, a node computer associated with the source gatewaymay be attempting to communication with a node computer that isassociated with the target gateway which may be located in anothernetwork that may not be directly reachable by the source gatewaycomputer. Accordingly, in one or more of the various embodiments, thesource gateway computer may attempt to employ a relay computer tofacilitate communication the target gateway computer.

Note, in one or more of the various embodiments, policy informationprovided by the management platform server may include information usedby the source gateway computer to determine if the node computer tryingto be reached is associated with the target gateway computer.

At block 906, in at least one of the various embodiments, a connectionmay be established between the relay computer and the source gatewaycomputer. In one or more of the various embodiments, the source gatewaymay initiate a connection handshake with a relay computer. As discussedabove, in some embodiments, there may be more than one relay computerreachable by the source gateway computer. Accordingly, in such cases,the source gateway computer may be arranged to broadcast the initialhandshake packets to all reachable relay computers. Note, in one or moreof the various embodiments, the term broadcast is used generally. Insome embodiments, a gateway computer may be arranged attempt to reachrelay computers via one or more network interfaces, networks, radios,protocols, services, or the like. For example, if a network or networkprotocol natively supports a broadcasting, the gateway computer maybroadcast the handshake using the native facilities of that network. Inother embodiments, the gateway computer may be provided a list ofavailable relay computers by a management platform server, or the like.For examples, policy information provided by a management platformserver may include a list of authorized relay computers as well asconditions/rules for accessing them. Note, such information may includenetwork address information, credentials, or the like, that may berequired communicate the handshake information.

Further, in some embodiments, relays computers may be accessible overdifferent network interfaces or radios (e.g., localhost, Ethernet, WiFi,BlueTooth, or the like). Accordingly, in one or more of the variousembodiments, gateway computers may be arranged to broadcast handshakerequests on each individual interface. For example, a gateway computermay be configured to “broadcast” handshake messages to variousinterfaces, such as, its localhost interface, a WiFi interface, two ormore cellular data networks, or the like. Thus, in this example, theunderlying broadcast mechanism or protocol may be selected to beconsistent with a given interface. In some embodiments, overlay networkengines, such as overlay network engine 322 or network routing engines,such as, network routing engine 326 may be arranged to provide a commoninterface (See, FIG. 5) that transparently formats and sends handshakemessages over the various network interfaces, radios, or the like, thatmay be available to a gateway computer.

In one or more of the various embodiments, gateway computer may bearranged to apply various conditions or rules to determine which relaycomputer to contact. Also, in some embodiments, gateway computers may bearranged to apply other conditions or rules to determine which answeringrelay (if any) to employ. For example, in some embodiments, gatewaycomputers may be arranged to accept the first relay computer thatprovides it a valid response.

Accordingly, in one or more of the various embodiments, a gatewaycomputer that needs a relay computer may be likely to receive a firstresponse from a relay computer that may be best suited to service thegateway computer. For example, since the first response to the gatewaycomputer handshake request is likely to be provided by a relay computerthat is closest to the requesting gateway computer. Likewise, in someembodiments, overloaded relay computers may be slower to respond thanunder-utilized relay computers. Thus, in some embodiments, using afirst-to-answer policy for selecting relay computers may automaticallyprovide load or resource balancing that improves the performance of theoverlay network.

Accordingly, in one or more of the various embodiments, a handshake mayinclude an initiation request that may be provided to a relay computerfrom a source gateway computer. In some embodiments, the initiationrequest may include an “Initiator 1” or “I1” packet, which includes atleast and a pair of GIDs, one GID associated with the source gatewaycomputer and one GID associated with the target gateway computer.Network address information, such as, an IP address and a port may beextracted from the sender/source network address information that may beincluded in the “I1” packet. Subsequent handshake messages may includean ingress identifier (e.g., SPI) value.

For example, if IP networking is being used, the source address of theIP packets sent by the source gateway computer may be used to providethe network address information for the source gateway computer. In thisway, the true, an addressable network address (e.g., the IP address andport) of the source gateway computer may be determined by each relaycomputer that receives the handshake request. In one embodiment, thepair of GIDs, the ingress identifier value, and the network address maybe stored in a data object, such as, data object 702.

In one or more of the various embodiments, a relay computer may bearranged to use cryptographic functions to ensure security of thesystem. However, in some embodiments, cryptographic operations on aper-data-packet basis would limit scalability. Accordingly, in someembodiments, the relay computer may be arranged to verify the signaturesof handshake packets, such as “I1”. In some embodiments, handshakepackets maybe signed by the private key corresponding to thepublic/private key pair identity for each gateway computer.

At block 908, in one or more of the various embodiments, the targetgateway computer may be arranged to establish a connection with therelay computer. In one or more of the various embodiments, gatewaycomputers may be arranged to periodically establish connections to withone or more relay computers to provide them the information necessaryfor the relay computer to facilitate handshake or connections with othergateway computers in other networks.

Accordingly, in one or more of the various embodiments, an auto-connectrequest may be provided to one or more relay computers from a targetgateway computer. In one embodiment, once a management platform serverhas published a policy allowing an overlay network connection betweentwo gateway computers, network address information (e.g., IP addressesand ports) need to be determined for both gateway computers. Inembodiments where a source gateway computer initiates an initialconnection request, the target gateway computer may be arranged toautomatically send a connection request so that a relay can coordinatepackets between the two. In one embodiment the handshake request from atarget gateway computer described in block 908 may be similar to theactions described for block 906—an ingress identifier and networkaddress information may be extracted from the network packet(s)associated with connection from the target gateway computer, while theauto-connect request includes a pair of GIDs defining the source andtarget gateway computers. The extracted information may be stored in adata object, such as, data object 702.

At block 910, in one or more of the various embodiments, if theconnection attempt between the source gateway computer and the targetgateway computer is allowed by the current policy, control may flow toblock 912; otherwise, control may be returned to a calling process.

In one or more of the various embodiments, a decision is made whetherthe “I1” (handshake) requests are consistent with the policy provided bythe management platform server at block 902. In one or more of thevarious embodiments, an “I1” request may be considered consistent withpolicy if the pair of GIDs included in the handshake request appear as apair in the policy data object, e.g. In columns 610 and 612 of dataobject 608. In some embodiments, if an initiation request isinconsistent with policy, e.g. if the pair of gateway computers tryingto connect are absent data object 608, then the process continues to areturn block. Note, in some embodiments, relay computers may be arrangeddrop or otherwise ignore handshake request network packets that areinconsistent with policy.

Accordingly, in one or more of the various embodiments, if the handshakerequests are allowed by policy, then control continues to block 912,where the relay computer may be arranged to forward additional controlpackets between the source gateway computer and target gateway computer.For example, in some embodiments, the “I1” packets received at block 904may be forwarded on to the target gateway computer. In one embodiment,the “I1” packet (and any subsequent packets, control or data) mayforwarded by replacing source network address information (e.g., IPaddress and port) with the network address information (e.g., IP addressand port) of the relay computer, as well as replacing the destinationnetwork address information (e.g., IP address and port) with the networkaddress information associated with the target gateway computer.

At block 912, in one or more of the various embodiments, the relaycomputer may be arranged to forward control packets to or from thesource gateway computer and the target gateway computer. Accordingly, inone or more of the various embodiments, after the connection has beenestablished, data packets may be forwarded between the source gatewaycomputer and target gateway computer. In one embodiment, as discussedabove with regard to block 910 above, the data packets may be forwardedby replacing source network address information (e.g. IP address andport) with the network address information (e.g., IP address and port)of the relay computer, as well as replacing the destination networkaddress information (e.g., IP address and port) with the network addressinformation (e.g., IP address and port) of the target gateway computer.

In one embodiment, an overlay network engine may be arranged such thatthe actual payload traffic between two gateway computers may betypically, but not necessarily, protected with a secure communicationprotocol, such as, IPsec. Accordingly, GIDs may be used to create IPsecSecurity Associations (SAs) and to authenticate the gateway computers.If IPsec is used, the actual payload packets remain compatible withstandard IPsec-protected IP packets. Thus, in one or more of the variousembodiments, they may reliably be used across networks. Next, controlmay be returned to a calling process.

It will be understood that each block of the flowchart theillustrations, and combinations of blocks in the flowchartillustrations, can be implemented by computer program instructions.These program instructions may be provided to a processor to produce amachine, such that the instructions, which execute on the processor,create means for implementing the actions specified in the flowchartblock or blocks. The computer program instructions may be executed byone or more processors to cause a series of operational steps to beperformed by the one or more processors to produce acomputer-implemented process such that the instructions, which executeon the one or more processors to provide steps for implementing theactions specified in the flowchart block or blocks. The computer programinstructions may also cause at least some of the operational steps shownin the blocks of the flowcharts to be performed in parallel. Moreover,some of the steps may also be performed across more than one processor,such as might arise in a multi-processor computer system or multi-corecomputer system. In addition, one or more blocks or combinations ofblocks in the flowchart illustration may also be performed concurrentlywith other blocks or combinations of blocks, or even in a differentsequence than illustrated without departing from the scope or spirit ofthe invention.

Additionally, in one or more steps or blocks, may be implemented usingembedded logic hardware, such as, an Application Specific IntegratedCircuit (ASIC), Field Programmable Gate Array (FPGA), Programmable ArrayLogic (PAL), or the like, or combination thereof, instead of a computerprogram. The embedded logic hardware may directly execute embedded logicto perform actions some or all of the actions in the one or more stepsor blocks. Also, in one or more embodiments (not shown in the figures),some or all of the actions of one or more of the steps or blocks may beperformed by one or more hardware microcontrollers instead of a CPU. Inat least one embodiment, the one or more microcontrollers may directlyexecute its own embedded logic to perform actions and access its owninternal memory and its own external Input and Output Interfaces (e.g.,hardware pins and/or wireless transceivers) to perform actions, such asSystem On a Chip (SOC), or the like.

FIG. 10 illustrates a sequence diagram 1000 for overlay networkidentity-based relay in accordance with at least one of the variousembodiments. In one embodiment, process 1000 may be implemented bygateway computers, relay computers, node computers, management platformserver computers, or the like, as described above.

In this example, sequence 1000 begins with a management platform serversending update policy 902 to gateway computer A. In one embodiment, thepolicy defines which gateway computers may communicate with each other,and via which relay computers.

In this example, for some embodiments, gateway A sends a handshakerequest 1004 to a relay computer. The request may include an “I1”initial connection request packet for establishing a connection togateway computer B. In one embodiment, the initial connection requestpacket may be sent in response to receiving an updated policy from aplatform engine or management platform server.

Next, in this example, the relay computer may be arranged to check for apolicy 1006 corresponding to the handshake request. Specifically, therelay extracts the source GID and the target GID included in the initialconnection request packet and looks for a policy in a data object, suchas, data object 602 that includes this pair of GIDs. However, in thisexample, since the relay has not received an updated policy,initialization request 1004 is dropped. Eventually, after some number ofretries, gateway computer A will determine that initialization request1004 was dropped or otherwise rejected by the relay computer. In thisscenario, gateway computer A may attempt to generate handshake requestpacket to resend a later time, after the relay computer has had a chanceto receive an updated policy.

Next, in this example, a management platform server may distribute anupdated policy 1008 to the relay computer. In this example, the updatedpolicy may be considered the same policy received already by gatewaycomputer A. In one embodiment, GID pairs found in the updated policy maybe used to populate policy data objects such as data object 602.

Next, in this example, Initialization request 1010 may be transmittedfrom gateway computer A to the relay computer. This request is similarto, if not identical to, Initialization request 1004. However, in theintervening time, the relay computer may be considered to have itspolicy updated, and so now the policy check for the GIDs contained ininitialization request 1010 succeeds.

However, in this example, the check for network address 1012 does notsucceed, as the relay has yet to receive an “auto connect” initialconnection request from gateway computer B, and as such the relaycomputer does not know the ingress identifier or network addressinformation of gateway computer B. Consequently, initialization request1010 is dropped or otherwise rejected by the relay computer. In thisscenario, gateway computer A may attempt to generate another initialconnection request packet to resend at a later time.

Next, in this example, the management platform server may transmitupdated policy 1014 to gateway computer B. The updated policy may beconsidered to be the same policy received already by gateway computer Aand the relay.

In response to update policy 1014, gateway computer B may initiate anauto connect 1016 to provide connection information to the relaycomputer. In some embodiments, auto connect 1016 may include informationthat indicates a pair of gateway computers that may be allowed tocommunicate with each other. For example, GIDs associated with gatewaycomputer A and gateway computer B may be extracted from the networktraffic associated with auto connect 1016. The relay computer may alsoobtain the ingress identifier, source gateway computer network addressinformation and store the resulting data in a policy data object such asdata object 602.

Next, in this example, gateway computer A may transmit initialconnection request packet 1018 to the relay computer. At this point, inthis example, policy exists to allow gateway computer A to connect withgateway computer B. Also, the network address information has beenextracted for gateway B, and so the previous conditions 1006 and 1012are satisfied. As such, an ingress identifier and source network addressinformation may be obtained from connection request 1018 and stored in adata object, such as, data object 602. At this point, ingressidentifiers and network address information have been obtained andstored in data object 602.

Next, in this example, the initial connection request packet 1018 maymodified to create initial connection request packet 1020. Specifically,in this example, source network address information may be overwrittenwith the network address information associated with the relay computer.Similarly, a destination network address information may be overwrittenwith the network address information associated with the target gatewaycomputer. Next, initial connection request packet 1020 may be forwardedto gateway computer B. Gateway computer B may, in one embodiment,respond with an “r1” packet, short for “responder1”.

Next, in this example, control traffic may be forwarded between gatewaycomputer A and gateway computer B. This control traffic may include, forexample, an “Initiator 2” packet and a “responder 2” packet, after whicha four part handshake has been completed and the connection isactivated.

Next, in this example, data traffic 1024 may be forwarded betweengateway computer A and gateway computer B. Accordingly, the targetgateway computer may forward the traffic to the appropriate nodecomputer. In some embodiments, the data traffic may include ESP(Encapsulating Security Payload) traffic.

In one embodiment, network traffic sent and received from gatewaycomputer A may use one network address standard, such as, InternetProtocol version 4 (“IPv4”), while packets sent and received fromgateway computer B may use a different network addressing scheme, suchas, Internet Protocol version 6 (“IPv6”). In one embodiment, forwardingcontrol traffic or data traffic between gateway computer A and gatewaycomputer B may include the relay computer translating between thedifferent network addressing conventions or standards. For example, insome embodiments, a relay computer may be arranged to translate IPv4packets to and from IPv6 packets, without encapsulating one packetwithin another.

In one or more of the various embodiments, if data traffic 1024 hasceased or at least paused for a long time, keep-alive packets 1026-1032may be exchanged to keep a connection between gateway computer A andgateway computer B open. However, if data traffic should begin againover the connection, the transmission of keep-a-lives packets may ceasebecause they may be unnecessary.

Next, in this example, the relay computer may become unreachable 1034.In some embodiments, this may be due to one or more errors conditions,such as, network failure, network misconfigurations, user errors,equipment failures, power outages, or the like, or combination thereof.

Accordingly, In one or more of the various embodiments, after the relaycomputer becomes unreachable, both gateway computer A and gatewaycomputer B may be arranged to continue to send keep-alive packets 1036through 1044. For example, in one embodiment, relay computer or gatewaycomputers may be arranged to send keep-alive packets every 15 secondsfor 45-60 seconds. If, as depicted in FIG. 10, the keep-alive packetsare not acknowledged the relay computer, one or both of gateway computerA or gateway computer B may attempt to reconnect to other relaycomputers 1050, beginning the described sequence once again starting atUpdate Policy 1002.

What is claimed as new and desired to be protected by Letters Patent ofthe United States is:
 1. A method for managing communication over anetwork using one or more network computers, wherein execution ofinstructions by the one or more network computers perform the methodcomprising: instantiating a relay engine to perform actions including:determining a connection route for one or more received packets based ona source gateway identifier (GID) corresponding to a source gateway anda target GID associated with a target gateway, wherein the connectionroute is associated with both the source GID and the target GID, andwherein each GID is separate from a network address of the sourcegateway or the target gateway; and forwarding the one or more packetsprovided by the source gateway to the target gateway based on networkaddress information associated with the target gateway.